<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
  <meta content="Copyright &copy; 2023 Thales. All Rights Reserved." name="copyright"/>
  <meta content="text/html;charset=utf-8" http-equiv="content-type"/>
  <meta content="text/css" http-equiv="Content-Style-Type"/>
  <title>
   Arcadia Reference - Agility in Engineering Course
  </title>
  <link href="../../scripts/jquery-treeview/jquery.treeview.css" rel="stylesheet"/>
  <script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript">
  </script>
  <script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript">
  </script>
  <link href="../../css/simpletree.css" rel="stylesheet" type="text/css"/>
  <link href="../../css/content.css" media="screen, projection" rel="stylesheet" title="default" type="text/css"/>
  <style>
   body {}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
  </style>
 </head>
 <body>
  <img src="../icon/logo_arcadia_small.png" style="float:left;width:50px;height:50px;"/>
  <nav>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#">
    ARCADIA
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#landscape">
    Engineering Landscape
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#userGuide">
    User Guide
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#reference">
    Reference Manual
   </a>
  </nav>
  <p>
   <br/>
  </p>
  <div id="content">
   <img alt="FunctionalChain" src="../icon/FunctionalChain.png" style="float:left; margin-right:10px"/>
   <h1>
    <a href="../ARCADIA/bc725e6691d44e039f7dca12bb360251.html">
     Agility in Engineering Course
    </a>
   </h1>
   <p style="margin-top:3px; margin-bottom:3px">
    <span class="elementMetaClass">
     Engineering Process
    </span>
    <p>
    </p>
   </p>
   <em class="elementPath">
    <a href="../ARCADIA/ad8c8a109fa64f039584c15108639254.html">
     Engineering Capabilities
    </a>
    &gt;
    <a href="../ARCADIA/4e8472cf52d44160a41ed722c73b1861.html">
     Support  Collaboration in Engineering
    </a>
    &gt;
    <a href="../ARCADIA/bc725e6691d44e039f7dca12bb360251.html">
     Agility in Engineering Course
    </a>
   </em>
   <p>
    <p>
     <strong>
      Challenge: How to build a path to a successful integration of agility within solution engineering
     </strong>
     .
    </p>
    <ul>
     <li>
      Define contents of agile increments based on valued capabilities
     </li>
     <li>
      Analyse impact of each one and preserve an (evolutive)&nbsp;vision of final solution architecture
     </li>
     <li>
      Align increments contents with IVV strategy and scheduling
     </li>
     <li>
      Maintain both incremental and final visions aligned
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
   </p>
   <h2>
    Related Diagrams
   </h2>
   <div>
    <p class="diagram-name" id="_oLTDYJUeEeqxb5_tqwKmHg">
     6  Agility in Engineering Course
    </p>
    <p class="diagram">
     <img alt="6  Agility in Engineering Course" src="bc725e6691d44e039f7dca12bb360251/_oLTDYJUeEeqxb5_tqwKmHg.jpg" usemap="#6  Agility in Engineering Course__oLTDYJUeEeqxb5_tqwKmHg_PositionMap"/>
     <br/>
     <br/>
     <map name="6  Agility in Engineering Course__oLTDYJUeEeqxb5_tqwKmHg_PositionMap">
      <area alt="38c7424f5c11476490db367b0b43bc42" coords="790,92,890,142" group="38c7424f5c11476490db367b0b43bc42" href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#id38c7424f-5c11-4764-90db-367b0b43bc42" shape="rect"/>
      <area alt="0f400333e4604c16a797eb161de26e50" coords="700,183,800,233" group="0f400333e4604c16a797eb161de26e50" href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html#id0f400333-e460-4c16-a797-eb161de26e50" shape="rect"/>
      <area alt="487b3ab24b0e40bbb70daded98286d3f" coords="600,93,731,143" group="487b3ab24b0e40bbb70daded98286d3f" href="../ARCADIA/487b3ab24b0e40bbb70daded98286d3f.html#id487b3ab2-4b0e-40bb-b70d-aded98286d3f" shape="rect"/>
      <area alt="4f8b5a2854014b0fac95b1715b6b0469" coords="210,92,321,142" group="4f8b5a2854014b0fac95b1715b6b0469" href="../ARCADIA/4f8b5a2854014b0fac95b1715b6b0469.html#id4f8b5a28-5401-4b0f-ac95-b1715b6b0469" shape="rect"/>
      <area alt="c354668558fc433fa1124e7b02e6bc7f" coords="10,92,110,142" group="c354668558fc433fa1124e7b02e6bc7f" href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html#idc3546685-58fc-433f-a112-4e7b02e6bc7f" shape="rect"/>
      <area alt="38c7424f5c11476490db367b0b43bc42" coords="400,92,500,142" group="38c7424f5c11476490db367b0b43bc42" href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#id38c7424f-5c11-4764-90db-367b0b43bc42" shape="rect"/>
      <area alt="d260034d335e47c98fbec6f97f023fa3" coords="210,183,321,233" group="d260034d335e47c98fbec6f97f023fa3" href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html#idd260034d-335e-47c9-8fbe-c6f97f023fa3" shape="rect"/>
      <area alt="fb4a1233e07c4fdfa6a376293041489c" coords="400,183,500,233" group="fb4a1233e07c4fdfa6a376293041489c" href="../ARCADIA/fb4a1233e07c4fdfa6a376293041489c.html#idfb4a1233-e07c-4fdf-a6a3-76293041489c" shape="rect"/>
     </map>
    </p>
    <p class="diagram-description">
     <p>
      This figure describes
     </p>
     <p>
      <strong>
       How to build a path to a successful integration of agility within solution engineering
      </strong>
      .
     </p>
     <ul>
      <li>
       Define contents of agile increments based on valued capabilities
      </li>
      <li>
       Analyse impact of each one and preserve an (evolutive)&nbsp;vision of final solution architecture
      </li>
      <li>
       Align increments contents with IVV strategy and scheduling
      </li>
      <li>
       Maintain both incremental and final visions aligned
      </li>
     </ul>
     <p>
      Define increments at solution engineering level, based on Capabilities and Value Analysis.
     </p>
     <p>
      Keep coherency with IVV Strategy.
     </p>
     <p>
      Drive software agile backlog accordingly; feed EPICs and User Stories based on Capabilities, and their descriptive functional chains and scenarios, appropriately cut into increment-size chunks if needed.
     </p>
     <p>
      For each step of this process, involving an engineering task or activity, the description gives some hints and methological recommendations. These recommendations are complementary with the description of the involved activity per se, in the context of the engineering concern and the process.
     </p>
    </p>
   </div>
   <h2>
    Contribution of each engineering activity to this process
   </h2>
   <table>
    <tr>
     <th>
      Engineering activity
     </th>
     <th>
      Specifics of activity for this process
     </th>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html">
       Perform SYSTEM NEED ANALYSIS
      </a>
     </td>
     <td>
      <p>
       Capabilities or Functional Chains describing customers/users expectations in System Need Analysis are a good support to both capture their expected value, and drive agile increments contents in a value-driven approach. Each of them should be valued, and development ordered according to this expected value (e.g. highest Business Value, highest Criticality first).
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/4f8b5a2854014b0fac95b1715b6b0469.html">
       Explore Solution Space &amp; Alternatives
      </a>
     </td>
     <td>
      <p>
       Build the solution in an incremental way based on value creation, using end-to-end Functional Chains and Scenarii. Develop the necessary and sufficient engineering artefacts in an iterative &amp; incremental way.
      </p>
      <p>
       &nbsp;
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html">
       Design PHYSICAL ARCHITECTURE
      </a>
     </td>
     <td>
      <p>
       Maintain a vision of the architecture and product at completion, and confront each iteration to it.
      </p>
      <p>
       Update the vision according to evolution of engineering and development.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html">
       Define a Components IVVQ Strategy
      </a>
     </td>
     <td>
      <p>
       IVV Strategy will use the definition of increments&nbsp;and sprints based on functional chains and scenarios, and sequence IVV activities accordingly.
      </p>
      <p>
       Conversely, IVV constraints or opportunities may influence definition of increments.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/fb4a1233e07c4fdfa6a376293041489c.html">
       Build IVV Test Suites and campaigns
      </a>
     </td>
     <td>
      <p>
       Test Campaigns and Test Cases are based on Capabilities, functional chains and scenarios feeding agile software development, hence securing coherency of IVV with system architecture and software.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/487b3ab24b0e40bbb70daded98286d3f.html">
       Define BUILDING STRATEGY - contracts for development &amp; IVVQ
      </a>
     </td>
     <td>
      <p>
       Define increments at solution engineering level, based on Capabilities and Value Analysis.
      </p>
      <p>
       Keep coherency with IVV Strategy.
      </p>
      <p>
       Drive software agile backlog accordingly; feed EPICs and User Stories based on Capabilities, and their descriptive functional chains and scenarios, appropriately cut into increment-size chunks if needed.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html">
       Perform SW engineering
      </a>
     </td>
     <td>
      <p>
       Define Agile Release content and Epics from the Functional Chains, being defined and refined in co-engineering.&nbsp;EPIC/User Stories used for &laquo;&nbsp;value&nbsp;&raquo; implementation scheduling. (TCE)
      </p>
      <p>
       Maintain a vision of software architecture, including the goal at completion, and update them at each sprint.
      </p>
     </td>
    </tr>
   </table>
   <h2>
    Diagrams displaying "Agility in Engineering Course"
   </h2>
   <ul>
    <li>
     <a href="../ARCADIA/bc725e6691d44e039f7dca12bb360251.html#_oLTDYJUeEeqxb5_tqwKmHg">
      6 - Agility in Engineering Course*
     </a>
    </li>
   </ul>
  </div>
 </body>
</html>
